# Contribute

_For security issues, please read the `Security.md` file._

[Describe welcomed contributions]

## Setup

[How to setup local development environment.]

[Brief file, and sub-directories, description.]

## Report Priority

As a solo maintainer, reports get prioritize according to

- Severity
- Number of users affected

## Issue Guidelines

Post a complete description of the issue using this template

```markdown
# Issue Title

## I did this
[self-contained example]

## I expected
[previous behavior]

## Instead got
[backtrace or behavior description]

## Already looked into
[quote documentation, closed issues or other forums]

## Project version
[project -V]

## Dependency versions
[OS, and other relevant dependencies]
```

Please make a documentation related pull request based on your question,
it's answer, and related discussion when appropriate. Alternatively,
submit bugs as test cases.

## Patch Guidelines

_Patches can be delivered as pull requests, or emails._

- All patches are contributed under `License.md`. Do not submit a patch
  if that isn't the case.
- Include tests for substantial bug fixes.
- Follow the style conventions of the surrounding code.
- Strip trailing white space.
- Update/add documentation.

## Code of Conduct

This code of conduct applies to all of the project's current, and future,
collaborative spaces, such as the hosted source code, it's issue tracker,
and official mirrors.

- Discussion should be limited to the project, and related technologies.
- Participants must ensure their language, and actions, are free of
  personal attacks and remarks disparaging to anyone.
- Behaviour which can be reasonably considered harassment will not be
  tolerated, and may result in being banned from these spaces.

You may report any violation to the project maintainer at
`:TODO: at example dot com`.
